This PR implements the functional requirements mentioned in the ticket #75.

The goal is to automatically restart or reload the config of all the geOrchestra applications when there is a new commit in the geOrchestra datadir. That would allow for easier management of the datadir in test environments.

The implementation includes a new component (datadirsync) that is deployed with certain permissions to access the
kubernetes API.

This component implements python code that actively listens to a given git repository, in a certain branch, at defined time intervals looking for changes in the repository. If this happens, it then invokes through the k8s API the rollout of the deployments listed in the deploymentSuffixNameList variable considering the predefined namespace.

Since in the context of Georchestra the SDI components update the datadir at initialization (https://github.com/georchestra/helm-georchestra/blob/main/templates/_bootstrap-georchestra-datadir.tpl) the rollout of a component guarantees that when restarting, it reloads the necessary configuration information.

The template accepts the definition of the username and password of the user with which the checks are made on the git repository, or that an sshkey is used (in which case it will be included in the corresponding container).

For details of the logic, review the template/datadirsync-deployment.yaml file.

The python implementation that executes the repository status check actions is momentarily in the following repository/folder https://github.com/jemacchi/simple-git-rollout-operator/tree/main/operator .

Initially, it was expected to perhaps create a somewhat more robust solution, but since it is a component that is not expected to be used in production environments, a simpler solution was chosen, which makes use of the Kubernetes API natively, with a component that does not involve CRD installation, and that has the minimum and necessary RBAC permissions to perform the relevant action.